Skip to content

Limit watchtower scope and integrate better with systemd#124

Open
rothgar wants to merge 1 commit into
bluesky-social:mainfrom
rothgar:watchtower
Open

Limit watchtower scope and integrate better with systemd#124
rothgar wants to merge 1 commit into
bluesky-social:mainfrom
rothgar:watchtower

Conversation

@rothgar

@rothgar rothgar commented Nov 4, 2024

Copy link
Copy Markdown

fixes #49

By not using oneshot service type and not detaching the docker compose command you can use normal systemd tools (e.g. journalctl) for logs. Docker commands still work too.

fixes bluesky-social#49

By not using oneshot service type and not detaching the docker compose
command you can use normal systemd tools (e.g. journalctl) for logs.
Docker commands still work too.

Signed-off-by: Justin Garrison <justinleegarrison@gmail.com>
@axfelix

axfelix commented Oct 31, 2025

Copy link
Copy Markdown
Contributor

Inclined to merge this, @bnewbold ?

@bnewbold

Copy link
Copy Markdown
Contributor

I think improvements here would be good, and these look like probably the right direction. I am not super familiar with watchtower, and know process monitoring stuff can be subtle.

I'd want somebody to do an independent pass over this to check the watchtower docs, and to try setting up a PDS this way and confirm sudo systemctl start/stop works as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Restrict Watchtower update to the containers specified in the compose file

3 participants